Add GCP and Azure variants of tls-scanner TLSAdherence jobs - #83196

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Walkthrough

Added GCP and Azure TLS 1.3 adherence coverage to periodic main jobs and optional OpenShift release tests. The configurations use cloud-specific profiles, compute types, strict adherence settings, scanner tests, and provider workflows.

Changes

TLS 1.3 adherence jobs

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• openshift/release#82659: Adds Azure-specific TLS scanner jobs with the same scanner tests.
• openshift/release#83172: Adds strict TLS 1.3 adherence scanner jobs with the same test steps.

❌ Failed checks (1 error)

_{Comment @coderabbitai help to get the list of available commands.}

[REHEARSALNOTIFIER]
@richardsonnick: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

/pj-rehearse

@richardsonnick: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

/pj-rehearse periodic-ci-openshift-tls-scanner-main-periodic-tls13-adherence-gcp

@richardsonnick: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardsonnick, smith-xyz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

/pj-rehearse ack

@richardsonnick: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

/pj-rehearse ack

@richardsonnick: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

/label rehearsals-ack

@richardsonnick: The label(s) /label rehearsals-ack cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, rebase/manual, cluster-config-api-changed, run-integration-tests, verified, ready-for-human-review, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/skip-dependent-bug-check, jira/valid-bug, ok-to-test, priority/ci-critical, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

/pj-rehearse ack

@richardsonnick: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@richardsonnick: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard.